SCORM manifest reconciliation

ABSTRACT

A method, system and computer-program product for deploying a package of objects in a learning management system. The method includes the steps of transmitting a Shareable Content Object Reference Model (SCORM) package to a SCORM Learning Management System (LMS); parsing out from the SCORM package a copy of a list of resources needed to deploy the SCORM package from the LMS; comparing names of all resources needed to deploy the SCORM package with an inventory of resources available to the LMS; in response to a name of one of the resources needed to deploy the SCORM package not matching any name in the inventory of resources available to the LMS, updating the name of the non-matching named resource to match a name of a resource in the inventory of resources available to the LMS; and deploying the SCORM package by launching the SCORM package with the corrected list of resources.

BACKGROUND OF THE INVENTION

1. Technical Field

The present invention relates in general to the field of computers andsimilar technology systems, and in particular to software utilized bysuch systems to implement methods and processes. Still moreparticularly, the present invention relates to reconciliation ofresource names in a SCORM environment.

2. Description of the Related Art

The Sharable Content Object Reference Model (SCORM) is an XML-basedframework that is aimed at fostering the development of reusablelearning content in “instructional objects” within a common frameworkfor computer and Web-based learning. SCORM uses Shareable ContentObjects (SCOs) and Learning Management Systems (LMSs) to delivereducational content to a student's computer. SCORM has been developed bythe Advanced Distributed Learning (ADL) initiative, whose specificationfor SCORM is herein incorporated by reference in its entirety.

An SCO is a standardized reusable learning object that includes (eitherphysically or by reference) a collection of one or more assets (e.g., aweb page, graphic files, a document, audio/video files, etc.). One ormore SCOs are packaged together as a course component, which isdelivered to an LMS, which is software that automates the administrationand delivery of the educational content for on-line learning. The LMSmanages student registration and log-ins, manages course catalogs,records test results from on-line students, and prepares grade/progressreports.

Referring then to FIG. 1, a exemplary SCORM environment 100 is depicted.Multiple SCOs 102 are combined into a SCORM package 104, which is thensent to LMS 106 for delivery to a student's computer 108. The student'scomputer 108 is thus presented with the education content, which mayinclude interactive videos, real-time video/audio feeds, web pages,written documents, graphic files, etc. LMS 106 also communicates with aneducator's computer 110, providing grades, student registrationinformation, etc. for the SCORM package 104 to a teacher/administratorusing educator's computer 110.

Part of the SCORM package 104 is an imsmanifest.xml file 112. File 112is an eXtensible Markup Language (XML) file that includes a listing ofall resources that must be deployed/executed by LMS 106 in order forSCORM package 104 to properly run. Resources listed in imsmanifest.xmlfile 112 include, for example, graphic files, web pages, documents,Javascript files, etc. LMS 106 includes a package inventory 114 listingall resources available to LMS 106. When the SCORM package 104 isreceived by LMS 106, package inventory 114 is checked by 106, andresources are deployed and/or pointed to for use by SCORM package 104.

A problem with LMS 106, as presented in the SCORM specificationreferenced above, is that resources named in imsmanifest.xml file 112must precisely match those resources found in package inventory 114. Ifthe resource names do not match precisely, then a “404 File Not Found”error will be returned, and the SCORM package 104 is not able to deploy.When operating in a UNIX® environment, this matching precision includescasing (whether letters are in upper case or lower case). In a Windows®environment, casing is not an issue, since Windows® is not casesensitive. However, many SCORM packages are developed in a Windows®environment and thus, when transported over to a UNIX® environment,often have “404 File Not Found” errors pop up for the first time.Similarly, whether in Windows® or UNIX®, simple typographical errors(incorrect letters/numbers in a file name) can cause similar “404”errors to occur.

SUMMARY OF THE INVENTION

Recognizing the problems associated with LMS in the SCORM environmentfor finding proper resources, the present invention presents acomputer-implementable method, system and computer-program product fordeploying a package of objects in a learning management system. Themethod includes the steps of transmitting a Shareable Content ObjectReference Model (SCORM) package to a SCORM Learning Management System(LMS); parsing out from the SCORM package a copy of a list of resourcesneeded to deploy the SCORM package from the LMS; comparing names of allresources needed to deploy the SCORM package with an inventory ofresources available to the LMS; in response to a name of one of theresources needed to deploy the SCORM package not matching any name inthe inventory of resources available to the LMS, updating the name ofthe non-matching named resource to match a name of a resource in theinventory of resources available to the LMS; and deploying the SCORMpackage by launching the SCORM package with the corrected list ofresources.

The above, as well as additional purposes, features, and advantages ofthe present invention will become apparent in the following detailedwritten description.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features believed characteristic of the invention are setforth in the appended claims. The invention itself, however, as well asa preferred mode of use, further purposes and advantages thereof, willbest be understood by reference to the following detailed description ofan illustrative embodiment when read in conjunction with theaccompanying drawings, where:

FIG. 1 depicts a prior art Shareable Content Object Reference Model(SCORM) environment;

FIG. 2 illustrates a novel SCORM environment having a manifest conformerin a SCORM Learning Management System (LMS);

FIG. 3 depicts a flow-chart of exemplary steps taken to conform amanifest in a SCORM message with resources available to the SCORM LMS;

FIG. 4 illustrates an exemplary computer in which the present inventionmay be implemented;

FIG. 5 depicts an exemplary server from which software for executing thepresent invention may be deployed;

FIGS. 6 a-b show a flow-chart of steps taken to deploy software capableof executing the steps shown and described in FIGS. 2-3;

FIGS. 7 a-c show a flow-chart of steps taken to deploy in a VirtualPrivate Network (VPN) software that is capable of executing the stepsshown and described in FIGS. 2-3;

FIGS. 8 a-b show a flow-chart showing steps taken to integrate into ancomputer system software that is capable of executing the steps shownand described in FIGS. 2-3; and

FIGS. 9 a-b show a flow-chart showing steps taken to execute the stepsshown and described in FIGS. 2-3 using an on-demand service provider.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

With reference now to FIG. 2, SCORM environment 100 is depicted with LMS106 having an imsmanifest.xml file conformer 202. File conformer 202causes non-conforming resources in imsmanifest.xml file 112 to beamended to come into conformance with resources available to LMS 106 (asfound in package inventory 114).

Steps taken in an exemplary embodiment of the present invention areshown in FIG. 3. After initiator block 302, SCORM LMS 106 receives aSCORM package 104. Within SCORM package 104 is a manifest listing ofresources needed by SCORM package 104 to properly execute. This manifestlisting is an XML file named “imsmanifest.xml” according to the SCORMspecification.

In order to have a non-executable non-corruptible copy of“imsmanifest.xml” to work with, LMS 106 parses out a copy of“imsmanifest.xml” from the SCORM package 104 to create a back-up copy of“imsmanifest.xml” (block 306). LMS 106 then iterates (inspects) throughall files and folders in the “imsmanifest.xml” file to create aninventory listing of all resources (e.g., web pages, Javascript files,documents, drivers, graphics files, audio files, etc.) needed by SCORMpackage 104 to properly execute (block 308).

LMS then compares all resources identified by the iteration of the“imsmanifest.xml” file with those known to be available to LMS 106,according to their presence in the “href” attribute file 204 in apackage inventory 202 in LMS 106 (block 310). If all of the resourcenames found in “imsmanifest.xml” match resource names found in the“href” attribute file (query block 312), then the SCORM package isdeployed with no further steps taken (block 314), and the steps end(terminator block 316).

However, the resource names may not match. For example, some of thecharacters in the “imsmanifest.xml” file may be in upper/lower case,which casing does not match the same characters in the “href” attributefile. This scenario of non-matching casing is especially prevalent whenthe SCORM package was originally created in a Windows® environment,which is casing agnostic. In UNIX®, however, such non-conforming casing(upper/lower case of characters) is fatal to LMS 106 when trying to findthe named resource. Similarly, there may be another typographical error(substituting one character for another entirely differentcharacter—irrespective of casing) in the “imsmanifest.xml” file. Thatis, the name of the non-matching named resource may fail to match thename of the resource in the inventory of resources available to the LMSdue to one or more of the characters in the names being different ASCIIcharacters (e.g., “a” instead of “e”). While slower and requiringadditional logic, these errors may also be caught and corrected by“imsmanifest.xml” conformer 202. Thus, as described in block 318,resource names in the “imsmanifest.xml” back-up copy file (created inthe step described in block 306) that do not match perfectly with theresource names in the “href” attribute file in package inventory 114 areautocorrected in the original “imsmanifest.xml” file received in SCORMpackage 104 (block 318). A system administrator is notified of thecorrection in a log file (block 320), and the SCORM package is deployed(block 314).

With reference now to FIG. 4, there is depicted a block diagram of anexemplary client computer 402, in which the present invention may beutilized. Client computer 402 includes a processor unit 404 that iscoupled to a system bus 406. A video adapter 408, which drives/supportsa display 410, is also coupled to system bus 406. System bus 406 iscoupled via a bus bridge 412 to an Input/Output (I/O) bus 414. An I/Ointerface 416 is coupled to I/O bus 414. I/O interface 416 affordscommunication with various I/O devices, including a keyboard 418, amouse 420, a Compact Disk-Read Only Memory (CD-ROM) drive 422, a floppydisk drive 424, and a flash drive memory 426. The format of the portsconnected to I/O interface 416 may be any known to those skilled in theart of computer architecture, including but not limited to UniversalSerial Bus (USB) ports.

Client computer 402 is able to communicate with a service providerserver 502 via a network 428 using a network interface 430, which iscoupled to system bus 406. Network 428 may be an external network suchas the Internet, or an internal network such as an Ethernet or a VirtualPrivate Network (VPN). Using network 428, client computer 402 is able touse the present invention to access service provider server 502.

A hard drive interface 432 is also coupled to system bus 406. Hard driveinterface 432 interfaces with a hard drive 434. In a preferredembodiment, hard drive 434 populates a system memory 436, which is alsocoupled to system bus 406. Data that populates system memory 436includes client computer 402's operating system (OS) 438 and applicationprograms 444.

OS 438 includes a shell 440, for providing transparent user access toresources such as application programs 444. Generally, shell 440 is aprogram that provides an interpreter and an interface between the userand the operating system. More specifically, shell 440 executes commandsthat are entered into a command line user interface or from a file.Thus, shell 440 (as it is called in UNIX®), also called a commandprocessor in Windows, is generally the highest level of the operatingsystem software hierarchy and serves as a command interpreter. The shellprovides a system prompt, interprets commands entered by keyboard,mouse, or other user input media, and sends the interpreted command(s)to the appropriate lower levels of the operating system (e.g., a kernel442) for processing. Note that while shell 440 is a text-based,line-oriented user interface, the present invention will equally wellsupport other user interface modes, such as graphical, voice, gestural,etc.

As depicted, OS 438 also includes kernel 442, which includes lowerlevels of functionality for OS 438, including providing essentialservices required by other parts of OS 438 and application programs 444,including memory management, process and task management, diskmanagement, and mouse and keyboard management.

Application programs 444 include a browser 446. Browser 446 includesprogram modules and instructions enabling a World Wide Web (WWW) client(i.e., client computer 402) to send and receive network messages to theInternet using HyperText Transfer Protocol (HTTP) messaging, thusenabling communication with service provider server 502.

Application programs 444 in client computer 402's system memory alsoinclude a UNIX SCORM Manifest Reconciler (USMR) 448.

USMR 448 includes code for implementing the processes described in FIGS.2-3. In one embodiment, client computer 402 is able to download USMR 448from service provider server 502.

The hardware elements depicted in client computer 402 are not intendedto be exhaustive, but rather are representative to highlight essentialcomponents required by the present invention. For instance, clientcomputer 402 may include alternate memory storage devices such asmagnetic cassettes, Digital Versatile Disks (DVDs), Bernoullicartridges, and the like. These and other variations are intended to bewithin the spirit and scope of the present invention.

As noted above, USMR 448 can be downloaded to client computer 402 fromservice provider server 502, shown in exemplary form in FIG. 5. Serviceprovider server 502 includes a processor unit 504 that is coupled to asystem bus 506. A video adapter 508 is also coupled to system bus 506.Video adapter 508 drives/supports a display 510. System bus 506 iscoupled via a bus bridge 512 to an Input/Output (I/O) bus 514. An I/Ointerface 516 is coupled to I/O bus 514. I/O interface 516 affordscommunication with various I/O devices, including a keyboard 518, amouse 520, a Compact Disk-Read Only Memory (CD-ROM) drive 522, a floppydisk drive 524, and a flash drive memory 526. The format of the portsconnected to I/O interface 516 may be any known to those skilled in theart of computer architecture, including but not limited to UniversalSerial Bus (USB) ports.

Service provider server 502 is able to communicate with client computer402 via network 428 using a network interface 530, which is coupled tosystem bus 506. Access to network 428 allows service provider server 502to execute and/or download USMR 448 to client computer 402.

System bus 506 is also coupled to a hard drive interface 532, whichinterfaces with a hard drive 534. In a preferred embodiment, hard drive534 populates a system memory 536, which is also coupled to system bus506. Data that populates system memory 536 includes service providerserver 502's operating system 538, which includes a shell 540 and akernel 542. Shell 540 is incorporated in a higher level operating systemlayer and utilized for providing transparent user access to resourcessuch as application programs 544, which include a browser 546, and acopy of USMR 448 described above, which can be deployed to clientcomputer 402.

The hardware elements depicted in service provider server 502 are notintended to be exhaustive, but rather are representative to highlightessential components required by the present invention. For instance,service provider server 502 may include alternate memory storage devicessuch as flash drives, magnetic cassettes, Digital Versatile Disks(DVDs), Bernoulli cartridges, and the like. These and other variationsare intended to be within the spirit and scope of the present invention.

Note further that, in a preferred embodiment of the present invention,service provider server 502 performs all of the functions associatedwith the present invention (including execution of USMR 448), thusfreeing client computer 402 from using its resources.

It should be understood that at least some aspects of the presentinvention may alternatively be implemented in a computer-useable mediumthat contains a program product. Programs defining functions on thepresent invention can be delivered to a data storage system or acomputer system via a variety of signal-bearing media, which include,without limitation, non-writable storage media (e.g., CD-ROM), writablestorage media (e.g., a floppy diskette, hard disk drive, read/write CDROM, optical media), and communication media, such as computer andtelephone networks including Ethernet, the Internet, wireless networks,and like network systems. It should be understood, therefore, that suchsignal-bearing media when carrying or encoding computer readableinstructions that direct method functions in the present invention,represent alternative embodiments of the present invention. Further, itis understood that the present invention may be implemented by a systemhaving means in the form of hardware, software, or a combination ofsoftware and hardware as described herein or their equivalent.

Software Deployment

Thus, the method described herein, and in particular as shown anddescribed in FIGS. 2-3, can be deployed as a process software fromservice provider server 502 (shown in FIG. 5) to client computer 402(shown in FIG. 4).

Referring then to FIG. 6, step 600 begins the deployment of the processsoftware. The first thing is to determine if there are any programs thatwill reside on a server or servers when the process software is executed(query block 602). If this is the case, then the servers that willcontain the executables are identified (block 604). The process softwarefor the server or servers is transferred directly to the servers'storage via File Transfer Protocol (FTP) or some other protocol or bycopying though the use of a shared file system (block 606). The processsoftware is then installed on the servers (block 608).

Next, a determination is made on whether the process software is to bedeployed by having users access the process software on a server orservers (query block 610). If the users are to access the processsoftware on servers, then the server addresses that will store theprocess software are identified (block 612).

A determination is made if a proxy server is to be built (query block614) to store the process software. A proxy server is a server that sitsbetween a client application, such as a Web browser, and a real server.It intercepts all requests to the real server to see if it can fulfillthe requests itself. If not, it forwards the request to the real server.The two primary benefits of a proxy server are to improve performanceand to filter requests. If a proxy server is required, then the proxyserver is installed (block 616). The process software is sent to theservers either via a protocol such as FTP or it is copied directly fromthe source files to the server files via file sharing (block 618).Another embodiment would be to send a transaction to the servers thatcontained the process software and have the server process thetransaction, then receive and copy the process software to the server'sfile system. Once the process software is stored at the servers, theusers, via their client computers, then access the process software onthe servers and copy to their client computers file systems (block 620).Another embodiment is to have the servers automatically copy the processsoftware to each client and then run the installation program for theprocess software at each client computer. The user executes the programthat installs the process software on his client computer (block 622)then exits the process (terminator block 624).

In query step 626, a determination is made whether the process softwareis to be deployed by sending the process software to users via e-mail.The set of users where the process software will be deployed areidentified together with the addresses of the user client computers(block 628). The process software is sent via e-mail to each of theusers' client computers (block 630). The users then receive the e-mail(block 632) and then detach the process software from the e-mail to adirectory on their client computers (block 634). The user executes theprogram that installs the process software on his client computer (block622) then exits the process (terminator block 624).

Lastly a determination is made on whether to the process software willbe sent directly to user directories on their client computers (queryblock 636). If so, the user directories are identified (block 638). Theprocess software is transferred directly to the user's client computerdirectory (block 640). This can be done in several ways such as, but notlimited to, sharing of the file system directories and then copying fromthe sender's file system to the recipient user's file system oralternatively using a transfer protocol such as File Transfer Protocol(FTP). The users access the directories on their client file systems inpreparation for installing the process software (block 642). The userexecutes the program that installs the process software on his clientcomputer (block 622) and then exits the process (terminator block 624).

VPN Deployment

The present software can be deployed to third parties as part of aservice wherein a third party VPN service is offered as a securedeployment vehicle or wherein a VPN is built on-demand as required for aspecific deployment.

A virtual private network (VPN) is any combination of technologies thatcan be used to secure a connection through an otherwise unsecured oruntrusted network. VPNs improve security and reduce operational costs.The VPN makes use of a public network, usually the Internet, to connectremote sites or users together. Instead of using a dedicated, real-worldconnection such as leased line, the VPN uses “virtual” connectionsrouted through the Internet from the company's private network to theremote site or employee. Access to the software via a VPN can beprovided as a service by specifically constructing the VPN for purposesof delivery or execution of the process software (i.e. the softwareresides elsewhere) wherein the lifetime of the VPN is limited to a givenperiod of time or a given number of deployments based on an amount paid.

The process software may be deployed, accessed and executed througheither a remote-access or a site-to-site VPN. When using theremote-access VPNs the process software is deployed, accessed andexecuted via the secure, encrypted connections between a company'sprivate network and remote users through a third-party service provider.The enterprise service provider (ESP) sets a network access server (NAS)and provides the remote users with desktop client software for theircomputers. The telecommuters can then dial a toll-bee number or attachdirectly via a cable or DSL modem to reach the NAS and use their VPNclient software to access the corporate network and to access, downloadand execute the process software.

When using the site-to-site VPN, the process software is deployed,accessed and executed through the use of dedicated equipment andlarge-scale encryption that are used to connect a company's multiplefixed sites over a public network such as the Internet.

The process software is transported over the VPN via tunneling which isthe process of placing an entire packet within another packet andsending it over a network. The protocol of the outer packet isunderstood by the network and both points, called tunnel interfaces,where the packet enters and exits the network.

The process for such VPN deployment is described in FIG. 7. Initiatorblock 702 begins the Virtual Private Network (VPN) process. Adetermination is made to see if a VPN for remote access is required(query block 704). If it is not required, then proceed to query block706. If it is required, then determine if the remote access VPN exists(query block 708).

If a VPN does exist, then proceed to block 710. Otherwise identify athird party provider that will provide the secure, encrypted connectionsbetween the company's private network and the company's remote users(block 712). The company's remote users are identified (block 714). Thethird party provider then sets up a network access server (NAS) (block716) that allows the remote users to dial a toll free number or attachdirectly via a broadband modem to access, download and install thedesktop client software for the remote-access VPN (block 718).

After the remote access VPN has been built or if it has been previouslyinstalled, the remote users can access the process software by dialinginto the NAS or attaching directly via a cable or DSL modem into the NAS(block 710). This allows entry into the corporate network where theprocess software is accessed (block 720). The process software istransported to the remote user's desktop over the network via tunneling.That is, the process software is divided into packets and each packetincluding the data and protocol is placed within another packet (block722). When the process software arrives at the remote user's desktop, itis removed from the packets, reconstituted and then is executed on theremote user's desktop (block 724).

A determination is then made to see if a VPN for site to site access isrequired (query block 706). If it is not required, then proceed to exitthe process (terminator block 726). Otherwise, determine if the site tosite VPN exists (query block 728). If it does exist, then proceed toblock 730. Otherwise, install the dedicated equipment required toestablish a site to site VPN (block 738). Then build the large scaleencryption into the VPN (block 740).

After the site to site VPN has been built or if it had been previouslyestablished, the users access the process software via the VPN (block730). The process software is transported to the site users over thenetwork via tunneling (block 732). That is the process software isdivided into packets and each packet including the data and protocol isplaced within another packet (block 734). When the process softwarearrives at the remote user's desktop, it is removed from the packets,reconstituted and is executed on the site user's desktop (block 736).The process then ends at terminator block 726.

Software Integration

The process software which consists of code for implementing the processdescribed herein may be integrated into a client, server and networkenvironment by providing for the process software to coexist withapplications, operating systems and network operating systems softwareand then installing the process software on the clients and servers inthe environment where the process software will function.

The first step is to identify any software on the clients and serversincluding the network operating system where the process software willbe deployed that are required by the process software or that work inconjunction with the process software. This includes the networkoperating system that is software that enhances a basic operating systemby adding networking features.

Next, the software applications and version numbers will be identifiedand compared to the list of software applications and version numbersthat have been tested to work with the process software. Those softwareapplications that are missing or that do not match the correct versionwill be upgraded with the correct version numbers. Program instructionsthat pass parameters from the process software to the softwareapplications will be checked to ensure the parameter lists matches theparameter lists required by the process software. Conversely parameterspassed by the software applications to the process software will bechecked to ensure the parameters match the parameters required by theprocess software. The client and server operating systems including thenetwork operating systems will be identified and compared to the list ofoperating systems, version numbers and network software that have beentested to work with the process software. Those operating systems,version numbers and network software that do not match the list oftested operating systems and version numbers will be upgraded on theclients and servers to the required level.

After ensuring that the software, where the process software is to bedeployed, is at the correct version level that has been tested to workwith the process software, the integration is completed by installingthe process software on the clients and servers.

For a high-level description of this process, reference is now made toFIG. 8. Initiator block 802 begins the integration of the processsoftware. The first tiling is to determine if there are any processsoftware programs that will execute on a server or servers (block 804).If this is not the case, then integration proceeds to query block 806.If this is the case, then the server addresses are identified (block808). The servers are checked to see if they contain software thatincludes the operating system (OS), applications, and network operatingsystems (NOS), together with their version numbers, which have beentested with the process software (block 810). The servers are alsochecked to determine if there is any missing software that is requiredby the process software in block 810.

A determination is made if the version numbers match the version numbersof OS, applications and NOS that have been tested with the processsoftware (block 812). If all of the versions match and there is nomissing required software the integration continues in query block 806.

If one or more of the version numbers do not match, then the unmatchedversions are updated on the server or servers with the correct versions(block 814). Additionally, if there is missing required software, thenit is updated on the server or servers in the step shown in block 814.The server integration is completed by installing the process software(block 816).

The step shown in query block 806, which follows either the steps shownin block 804, 812 or 816 determines if there are any programs of theprocess software that will execute on the clients. If no processsoftware programs execute on the clients the integration proceeds toterminator block 818 and exits. If this not the case, then the clientaddresses are identified as shown in block 820.

The clients are checked to see if they contain software that includesthe operating system (OS), applications, and network operating systems(NOS), together with their version numbers, which have been tested withthe process software (block 822). The clients are also checked todetermine if there is any missing software that is required by theprocess software in the step described by block 822.

A determination is made is the version numbers match the version numbersof OS, applications and NOS that have been tested with the processsoftware (query block 824). If all of the versions match and there is nomissing required software, then the integration proceeds to terminatorblock 818 and exits.

If one or more of the version numbers do not match, then the unmatchedversions are updated on the clients with the correct versions (block826). In addition, if there is missing required software then it isupdated on the clients (also block 826). The client integration iscompleted by installing the process software on the clients (block 828).The integration proceeds to terminator block 818 and exits.

On Demand

The process software is shared, simultaneously serving multiplecustomers in a flexible, automated fashion. It is standardized,requiring little customization and it is scalable, providing capacity ondemand in a pay-as-you-go model.

The process software can be stored on a shared file system accessiblefrom one or more servers. The process software is executed viatransactions that contain data and server processing requests that useCPU units on the accessed server. CPU units are units of time such asminutes, seconds, hours on the central processor of the server.Additionally the assessed server may make requests of other servers thatrequire CPU units. CPU units are an example that represents but onemeasurement of use. Other measurements of use include but are notlimited to network bandwidth, memory usage, storage usage, packettransfers, complete transactions etc.

When multiple customers use the same process software application, theirtransactions are differentiated by the parameters included in thetransactions that identify the unique customer and the type of servicefor that customer. All of the CPU units and other measurements of usethat are used for the services for each customer are recorded. When thenumber of transactions to any one server reaches a number that begins toaffect the performance of that server, other servers are accessed toincrease the capacity and to share the workload. Likewise when othermeasurements of use such as network bandwidth, memory usage, storageusage, etc. approach a capacity so as to affect performance, additionalnetwork bandwidth, memory usage, storage etc. are added to share theworkload.

The measurements of use used for each service and customer are sent to acollecting server that sums the measurements of use for each customerfor each service that was processed anywhere in the network of serversthat provide the shared execution of the process software. The summedmeasurements of use units are periodically multiplied by unit costs andthe resulting total process software application service costs arealternatively sent to the customer and or indicated on a web siteaccessed by the customer which then remits payment to the serviceprovider.

In another embodiment, the service provider requests payment directlyfrom a customer account at a banking or financial institution.

In another embodiment, if the service provider is also a customer of thecustomer that uses the process software application, the payment owed tothe service provider is reconciled to the payment owed by the serviceprovider to minimize the transfer of payments.

With reference now to FIG. 9, initiator block 902 begins the On Demandprocess. A transaction is created than contains the unique customeridentification, the requested service type and any service parametersthat further, specify the type of service (block 904). The transactionis then sent to the main server (block 906). In an On Demand environmentthe main server can initially be the only server, then as capacity isconsumed other servers are added to the On Demand environment.

The server central processing unit (CPU) capacities in the On Demandenvironment are queried (block 908). The CPU requirement of thetransaction is estimated, then the servers available CPU capacity in theOn Demand environment are compared to the transaction CPU requirement tosee if there is sufficient CPU available capacity in any server toprocess the transaction (query block 910). If there is not sufficientserver CPU available capacity, then additional server CPU capacity isallocated to process the transaction (block 912). If there was alreadysufficient available CPU capacity then the transaction is sent to aselected server (block 914).

Before executing the transaction, a check is made of the remaining OnDemand environment to determine if the environment has sufficientavailable capacity for processing the transaction. This environmentcapacity consists of such things as but not limited to networkbandwidth, processor memory, storage etc. (block 916). If there is notsufficient available capacity, then capacity will be added to the OnDemand environment (block 918). Next the required software to processthe transaction is accessed, loaded into memory, then the transaction isexecuted (block 920).

The usage measurements are recorded (block 922). The usage measurementsconsist of the portions of those functions in the On Demand environmentthat are used to process the transaction. The usage of such functionsas, but not limited to, network bandwidth, processor memory, storage andCPU cycles are what is recorded. The usage measurements are summed,multiplied by unit costs and then recorded as a charge to the requestingcustomer (block 924).

If the customer has requested that the On Demand costs be posted to aweb site (query block 926), then they are posted (block 928). If thecustomer has requested that the On Demand costs be sent via e-mail to acustomer address (query block 930), then these costs are sent to thecustomer (block 932). If the customer has requested that the On Demandcosts be paid directly from a customer account (query block 934), thenpayment is received directly from the customer account (block 936). TheOn Demand process is then exited at terminator block 938.

While the present invention has been particularly shown and describedwith reference to a preferred embodiment, it will be understood by thoseskilled in the art that various changes in form and detail may be madetherein without departing from the spirit and scope of the invention.Furthermore, as used in the specification and the appended claims, theterm “computer” or “system” or “computer system” or “computing device”includes any data processing system including, but not limited to,personal computers, servers, workstations, network computers, main framecomputers, routers, switches, Personal Digital Assistants (PDA's),telephones, and any other system capable of processing, transmitting,receiving, capturing and/or storing data.

1. A method of deploying a package of objects in a learning managementsystem, the method comprising: transmitting a Shareable Content ObjectReference Model (SCORM) package to a SCORM Learning Management System(LMS); parsing out from the SCORM package a copy of a list of resourcesneeded to deploy the SCORM package from the LMS; comparing names of allresources needed to deploy the SCORM package with an inventory ofresources available to the LMS; in response to a name of one of theresources needed to deploy the SCORM package not matching any name inthe inventory of resources available to the LMS, updating the name ofthe non-matching named resource to match a name of a resource in theinventory of resources available to the LMS; and deploying the SCORMpackage by launching the SCORM package with the corrected list ofresources.
 2. The method of claim 1, wherein the list of resourcesneeded to deploy the SCORM package is located in a SCORM“imsmanifest.xml” file that is part of the SCORM package.
 3. The methodof claim 1, wherein the name of the non-matching named resource fails tomatch the name of the resource in the inventory of resources availableto the LMS due to one or more of the characters in the names havingdifferent casing.
 4. The method of claim 1, wherein the name of thenon-matching named resource fails to match the name of the resource inthe inventory of resources available to the LMS due to one or more ofthe characters in the names being different characters.
 5. The method ofclaim 1, wherein one of the resources needed to deploy the SCORM packageis a driver.
 6. The method of claim 1, wherein one of the resourcesneeded to deploy the SCORM package is a Javascript file.
 7. A systemcomprising: a processor; a data bus coupled to the processor; and acomputer-usable medium embodying computer program code, thecomputer-usable medium being coupled to the data bus, the computerprogram code comprising instructions executable by the processor andconfigured for: transmitting a Shareable Content Object Reference Model(SCORM) package to a SCORM Learning Management System (LMS); parsing outfrom the SCORM package a copy of a list of resources needed to deploythe SCORM package from the LMS; comparing names of all resources neededto deploy the SCORM package with an inventory of resources available tothe LMS; in response to a name of one of the resources needed to deploythe SCORM package not matching any name in the inventory of resourcesavailable to the LMS, updating the name of the non-matching namedresource to match a name of a resource in the inventory of resourcesavailable to the LMS; and deploying the SCORM package by launching theSCORM package with the corrected list of resources.
 8. The system ofclaim 7, wherein the list of resources needed to deploy the SCORMpackage is located in a SCORM “imsmanifest.xml” file that is part of theSCORM package.
 9. The system of claim 7, wherein the name of thenon-matching named resource fails to match the name of the resource inthe inventory of resources available to the LMS due to one or more ofthe characters in the names having different casing.
 10. The system ofclaim 7, wherein one of the resources needed to deploy the SCORM packageis a driver.
 11. The system of claim 7, wherein one of the resourcesneeded to deploy the SCORM package is a web page.
 12. The system ofclaim 7, wherein one of the resources needed to deploy the SCORM packageis a Javascript file.
 13. A computer-usable medium embodying computerprogram code, the computer program code comprising computer executableinstructions configured for: transmitting a Shareable Content ObjectReference Model (SCORM) package to a SCORM Learning Management System(LMS); parsing out from the SCORM package a copy of a list of resourcesneeded to deploy the SCORM package from the LMS; comparing names of allresources needed to deploy the SCORM package with an inventory ofresources available to the LMS; in response to a name of one of theresources needed to deploy the SCORM package not matching any name inthe inventory of resources available to the LMS, updating the name ofthe non-matching named resource to match a name of a resource in theinventory of resources available to the LMS; and deploying the SCORMpackage by launching the SCORM package with the corrected list ofresources.
 14. The computer-useable medium of claim 13, wherein the listof resources needed to deploy the SCORM package is located in a SCORM“imsmanifest.xml” file that is part of the SCORM package.
 15. Thecomputer-useable medium of claim 13, wherein the name of thenon-matching named resource fails to match the name of the resource inthe inventory of resources available to the LMS due to one or more ofthe characters in the names having different casing.
 16. Thecomputer-useable medium of claim 13, wherein one of the resources neededto deploy the SCORM package is a driver.
 17. The computer-useable mediumof claim 13, wherein one of the resources needed to deploy the SCORMpackage is a web page.
 18. The computer-useable medium of claim 13,wherein one of the resources needed to deploy the SCORM package is aJavascript file.
 19. The computer-useable medium of claim 13, whereinthe computer program code is deployed to a client computer from a serverat a remote location.
 20. The computer-useable medium of claim 13,wherein the computer program code is provided by a service provider to acustomer on an on-demand basis.